Information on the latest Amiga Apache version can be found at http://www.dsdelft.nl/~apache. This will list the current release, any more recent beta-test release, together with details of mirror web and anonymous ftp sites.
If you downloaded the binary file from the Amiga Apache site, skip to Installing Apache. Otherwise read the next section on how to compile the server.
To compile Amiga Apache you need a full GeekGadgets (formerly ADE) environment with the latest Ixemul.library (47.2) includes and the GCC 2.7.2.1 release which can be downloaded at ftp.ninemoons.com/pub/geekgadgets/971125/amiga-bin/
All configuration of Apache is performed in the src
directory of the Apache distribution. Change into this directory.
Configuration
file. Uncomment lines corresponding to
those optional modules you wish to include (among the Module lines
at the bottom of the file), or add new lines corresponding to
additional modules you have downloaded or written. (See API.html for preliminary docs on how to
write Apache modules). Advanced users can comment out some of the
default modules if they are sure they will not need them (be careful
though, since many of the default modules are vital for the correct
operation and security of the server).
You should also read the instructions in the Configuration
file to see if you need to set any of the Rule
lines.
Configure
as given below (don't forget
to set the S bit by typing in a shell 'protect Configure RWEDS')
Run the Configure
script:
This generates a Makefile for use in stage 3. It also creates a Makefile in the support directory, for compilation of the optional support programs.% Configure Using 'Configuration' as config file + configured for <whatever> platform + setting C compiler to <whatever> * + setting C compiler optimization-level to <whatever> * + Adding selected modules + doing sanity check on compiler and options Creating Makefile in support Creating Makefile in main Creating Makefile in os/unix Creating Makefile in modules/standard
(If you want to maintain multiple configurations, you can give a
option to Configure
to tell it to read an alternative
Configuration file, such as Configure -file
Configuration.ai
).
make
.
httpd
in the
src
directory. Copy this binary to APACHE:
If you downloaded the binary file from the Amiga Apache site, unarchive the entire apache_1.3b3.lha file to the APACHE: directory. Open a shell and type:
lha -mraxe x apache_1.3b3.lha APACHE:(see the Before install page for instructions)
Amitcp: add the following in your db/services file: http 80/tcp and add a user http and a group http to your passwd and groupfile by editing the db/passwd and db/group files. db/passwd file: http|*|1001|45|WebMaster's Tool|apache:|cli db/group file: http|*|45|http Or use the easy Amitcp config script if you use Amitcp 4.3 + Miami: add the following in your database/services menu: Name: http Id: 80 protocol : tcp database/users menu: Username: http UserId : 45 GroupId : 45 Realname: Webmasters Tool homedir : apache and add a secure password! database/groups groupname: http groupid : 45 users : http
You need the user http and the group http in the configuration of apache! (in the httpd.conf to be precisely.
conf
, logs
and
icons
directories into it.
The next step is to edit the configuration files for the server. This
consists of setting up various directives in up to three
central configuration files. By default, these files are located in
the conf
directory and are called srm.conf
,
access.conf
and httpd.conf
. To help you get
started there are same files in the conf
directory of the
distribution, called srm.conf-dist
,
access.conf-dist
and httpd.conf-dist
. Copy
or rename these files to the names without the -dist
.
Then edit each of the files. Read the comments in each file carefully.
Failure to setup these files correctly could lead to your server not
working or being insecure. You should also have an additional file in
the conf
directory called mime.types
. This
file usually does not need editing.
First edit httpd.conf
. This sets up general attributes
about the server: the port number, the user it runs as, etc. Next
edit the srm.conf
file; this sets up the root of the
document tree, special functions like server-parsed HTML or internal
imagemap parsing, etc. Finally, edit the access.conf
file to at least set the base cases of access.
In addition to these three files, the server behavior can be configured
on a directory-by-directory basis by using .htaccess
files in directories accessed by the server.